Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade eslint-plugin-n from 16.0.0 to 16.0.1 #117

Merged
merged 1 commit into from
Jul 18, 2023

Conversation

lholmquist
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade eslint-plugin-n from 16.0.0 to 16.0.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2023-06-25.
Release notes
Package name: eslint-plugin-n
  • 16.0.1 - 2023-06-25
    • fix: Update all dependencies. Fix a few tests where eslint now reports nodeType: null. (44cec62)
  • 16.0.0 - 2023-05-16

    breaking changes

    • feat!: update default ecmaVersion to 2021 (#96) (49d3ee7)
    • feat!: engines.node defaults to 16.0.0 (#91) (075f0c5)
    • feat!: drop node.js < 16 (#90) (38a67ef)

    features

from eslint-plugin-n GitHub release notes
Commit messages
Package name: eslint-plugin-n
  • 44cec62 fix: Update all dependencies. Fix a few tests where eslint now reports nodeType: null.

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@pacostas
Copy link
Member

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants